Subscription change event failure handling enhancement

Resolved an issue where asynchronous subscription change events (for example - SUBSCRIPTION_CHANGE) remained in a pending state after being marked as failed through the API. This behavior previously required manual intervention to resolve, increasing operational overhead for partners.

Key changes

• Asynchronous events that fail through API are now immediately marked as non-recoverable (failed), regardless of event type or error code.
• No impact to existing synchronous event flows or error code-based recoverability logic.

Impact

• Applies only to ISVs using asynchronous event flows.
• Reduces manual intervention and improves system reliability.
• No breaking changes for synchronous events or error code handling logic.

Feature enablement

No feature enablement is required.

Setting enablement

No setting enablement is required.

Documentation

No documentation updates are required.